Methods and apparatus for interfacing to a data storage system

ABSTRACT

A data storage system includes methods and apparatus that provide volumes for access by host computing devices. The volumes can have a storage size that is independently configurable from an actual amount of data storage that may or may not be associated with the volume. The volumes also have a persistent identifier. The volumes can have any amount of associated storage space allocated to the volume, including none, within the data storage system. Since the storage size and associated storage space are each independently configurable from each other, host that interface with the data storage system can perceive the volumes as being larger than they really are. A dynamic volume configuration technique is provided which allows storage space within storage devices in the data storage system to be dynamically associated and disassociated (i.e., added and removed) from the volumes on an as-needed basis, without requiring disruption of host activities with respect to the volumes. The persistent identifier of a volume allows all hosts and other data storage systems to “see” the volume. This allows a volume in one data storage system to have associated storage space from another volume in another data storage system. Using these techniques, the invention allows software applications and operating systems on hosts that interface to the data storage system to perceive that a volume is always present on the data storage system, even if storage space understood to be associated with the volume from the host&#39;s perspective is allocated elsewhere or is non-existent.

CONTINUATION APPLICATION DATA

This application is a continuation of U.S. patent application Ser. No.10/623,103 entitled, “Methods and Apparatus for Interfacing To A DataStorage System,” filed Jul. 18, 2003 now U.S. Pat. No. 7,281,111 whichclaims priority to earlier filed U.S. patent application Ser. No.09/342,474, entitled “Methods and Apparatus for Interfacing To A DataStorage,” filed Jun. 29, 1999, the disclosure and teachings of which areincorporated in its entirety herein by reference.

FIELD OF THE INVENTION

The present invention relates generally to data storage systems, andmore particularly, to an interface mechanism which allows host computingdevices to interoperate with the data storage system.

BACKGROUND OF THE INVENTION

The widespread use of computerized data processing systems has createdvast amounts of data that must be stored. To serve this need, datastorage system providers have developed data storage systems that usetape or disk arrays to store such data. In a typical data storage systemusing disk or tape array technology, there can be many individualphysical storage devices, such as hard disk drives or tape drives.Circuitry and/or software in either the data storage system or in thehost computing devices (hosts) which interface to the data storagesystem can manipulate the way in which data is stored in the variousindividual storage devices. Various arrangements of the storage devicesand of the data maintained in each device are possible. Each arrangementgenerally allows the storage devices to appear as a single contiguousdata repository or as groups of repositories to an application executingon a host that requires storage or access to stored data.

By way of example, a data storage technology such as Redundant Arrays ofInexpensive Disks (RAID) allows a data storage system to presentconglomerations of many individual hard disk drives to host computingdevices as one or more disk storage areas. In general, the data storagesystem handles the RAID operations in such a way that they aretransparent to the host computing devices which interface to the datastorage system. RAID systems also provide various levels of faulttolerance, error correction and error recovery. This allows the hosts totreat a conglomeration of disks within the RAID data storage systemwithout regard to the underlying physical separation or layout of datawithin or “across” each individual disk drive. For more detailsconcerning RAID technology and systems which implement this technology,the reader is referred to Patterson et al., “A Case for Redundant Arraysof Inexpensive Disks (RAID),” ACM SIGMOND Conference, Jun. 1-3, 1988,the teaching of which are hereby incorporated by reference in theirentirety.

The conglomerations of disks presented as a single repository for datato a host computing device from a data storage system are calledvolumes. A prior art volume identifies and serves as a host interface tothe raw physical storage associated with one or more storage deviceswithin the data storage system. Typically, in the prior art, a personknown as a systems administrator configures one or more volumes duringan initial or periodic configuration process performed on the datastorage system. Between configurations, the total amount of availabledata storage within a prior art volume does not change. For instance, anadministrator may configure a data storage system containing fourphysically separate hard disk drives “A”, “B”, “C” and “D” to presentonly two volumes of data storage, V1 and V2, to a host computing devicethat interfaces to the data storage system. The first volume V1 may be aconglomeration of physical storage space (using RAID or anotherdata-over-multiple-disk technology) located on disks “A” and “B”, whilethe second volume V2 may be a conglomeration of storage space existingwithin hard disk drives “C” and “D”.

A single volume need not be comprised of space from more than onestorage device. For example, a volume might be comprised of only aportion of storage space from a single hard disk. In this case, thevolume may be equivalent, for example, to a partition, slice or otherapportionment of that hard disk.

In any event, prior art data storage systems provide volumes that areessentially interface mechanisms to a host computing device. Generally,in the prior art, a single host directly interfaces (i.e., via a SCSIbus or other connection mechanism) to the data storage system and“serves” the data from the data storage system onto a network for accessby other hosts, which do not directly interface to the data storagesystem. The volumes appear to the server host as individual contiguousrepositories for data. Within the data storage system, however, thevolumes may actually span portions of one or more storage devices (e.g.disk drives, tape drives, and so forth). Providing volumes insulatesserver software applications and server host computing devices from thedetails of complicated data and disk storage mechanisms such asmirroring, error correction, striping and so on. From here on in thisdescription, a host or host computing device generally refers to a host(i.e., a server) that directly interfaces with a data storage system.

Generally, when a host computing device starts-up or “boots”, anoperating system that controls the host polls any attached data storagesystems via device drivers to determine what volumes are available foraccess to the host computing device within the data storage system. Byway of example, a host executing a version of the Solaris operatingsystem (a variant of Unix), which is manufactured by Sun Microsystems ofMountain View, Calif., (Solaris being a registered trademark of SunMicrosystems Inc.) can use an operating system call, such as “reportLUNS” for a SCSI-3 device, to poll the SCSI port coupled to the datastorage system in order to determine volume availability. In response tothe host poll, the data storage system provides a list of availablevolumes in the given target device. Host-specific access informationstored in the volumes may be reported back to the host as well.

A host filesystem in the host computing device can then access aparticular volume by “mounting” a volume identifier associated with thevolume (obtained from the initial poll) that is provided from the datastorage system to a “mount point” within the host filesystem. Afilesystem mount point is essentially a stub directory within the hostfilesystem that serves as an entry point into the volume once the hosthas mounted the volume. After the host has mounted the volume, softwareapplications on the host can access data in the volume by referencingthe mount point directory and any subdirectories that are now availablewithin the mounted volume of data storage. For example, in a computingdevice controlled by the Unix operating system, a mount point maycorrespond to a directory within the Unix filesystem, such as “/home”. Asystem command such as

mount /home /dev/dsk/c0t0d0s0

can be used to mount the volume identified by “/dev/dsk/c0t0d0s0” to themount point “/home” in the Unix filesystem. After the volume is mounted,users or applications executing on the computing device can referencefiles and data within the /home directory and any subdirectories within/home that actually exist within the data storage associated with thevolume. That is, all data accessed within the /home directory isphysically maintained on storage space within storage devices (e.g.,hard disk drives) that are associated with the mounted volume“/dev/dsk/c0t0d0s0” in the data storage system.

Most operating systems rely on volumes provided by a data storage systemfor certain operations. For example, many host operating systems expectstorage space within volumes to be organized into sequential blocks ofdata ranging from Block 0 to Block N. Many operating systems frequentlystore certain host-specific volume directory information, partitioninformation, track/sector layout and size information, and so forth on apredetermined designated portion of storage space within a volume. Block0 (i.e. the first block) of a volume is frequently used for storing suchhost-specific data. As another example, the Microsoft Windows NToperating system, manufactured by Microsoft Corporation of Redmond,Wash., performs periodic checks to make sure that a mounted volume isalways accessible within the data storage system. Windows and Windows NTare registered trademarks of Microsoft Corporation.

Generally, once an operating system of a host computing device mounts aprior art volume, the host and/or the data storage system cannot changethe amount of available storage space (i.e. the size) within the volumewhile the volume remains mounted. Thus, if a host mounts a ten Gigabytevolume of data storage, the host operating system and any host softwareapplications can have access to the full ten Gigabytes of data storagewithin that volume as a single contiguous portion of storage space.However, the amount of data that can be stored on such a volume islimited to ten Gigabytes, less any space used for volume formattingrequirements, such as the Block 0 information. In order for more storagespace to be associated with (i.e. added to) the volume, a systemsadministrator for the host must unmount the volume and reconfigure thevolume size by associating additional storage devices to the volumewithin the data storage system. Once the systems administratorreconfigures the volume size, the systems administrator can againpresent the volume to the host operating system as available datastorage space.

Reconfiguration of a volume (i.e., to add or remove or move data storagespace) typically requires high-level systems administrator (e.g. “root”)privileges on the host computing device. For example, during volumereconfiguration, the host operating system must be brought into aspecial restricted user mode (e.g. single-user mode). The restricteduser mode ensures that no host application programs are attempting toaccess data within the volume while reconfiguration is in progress. Oncereconfigured, the host operating system may need to be re-started or“re-booted” in order for the operating system to re-poll the attacheddata storage system to discover the newly re-configured volume(s)containing the additional storage space.

The access information stored by a host operating system in Block 0 of avolume is often specific to a particular operating system or hostarchitecture. By way of example, if a version of the Solaris operatingsystem is used to configure and mount a volume, Block 0 of that volumemay contain Solaris-specific volume access information. If the datastorage system that contains the Solaris-specific volume is subsequentlyinterfaced with another host computing device that uses a differentoperating system or architecture, such as Microsoft Windows NT, theaccess information in Block 0 of the Solaris-specific volume may not besuitable to allow access to the volume by the Windows NT controlledcomputing device. This is because volume labeling information providedby Solaris in Block 0 of the volume is not be compatible with volumelabeling information required by Windows NT.

Certain software application programs that execute on host computingdevices also rely on the existence and correct operation of volumes. Forinstance, a data storage application called TimeFinder, manufactured byEMC Corporation of Hopkinton, Mass. (TimeFinder is a trademark of EMCCorporation), allows a data storage system to create and continuouslymaintain a mirror image volume of a master volume. While the mirrorimage volume is continuously being maintained as a copy of the mastervolume (reflecting all changes made to data within the master volume),both the mirror image volume and the master volumes are “visible” to thehost operating system that is interfaced to the data storage system.From time to time, the TimeFinder software can detach the mirror imagevolume from its synchronous relationship with the master volume.TimeFinder may detach the mirror image volume from the master volume,for example, to allow the mirror image volume to be used for offlineapplication testing or periodic backup purposes on dedicated backuphost. This allows the master volume to remain accessible the regularhost computing devices thus providing uninterrupted access to data inthe master volume. Such a system is valuable in mission critical systemsrequiring around-the-clock access to data. When the offline operations(i.e., backup or testing) on the mirror image volume are complete,TimeFinder reinstates the synchronous relationship between the mirrorimage volume and the master volume so that the mirror image volume canbe brought back up-to-date with the master volume to reflect any changesthat may have occurred in the master volume during the backup of testingprocessing.

As another example of the reliance on volumes for the proper operationof host software applications, certain host application programs mayrequire a minimum amount of storage space to be available within avolume before allowing processing within the application to proceed.This may be the case, for example, when a database program attempts toinitially access a volume of storage to create a new database. Thedatabase application may have minimum storage size requirements withrespect to the volume in order to allow processing to proceed beyond acertain point.

SUMMARY OF THE INVENTION

Prior art data storage systems that use conventional techniques tocreate, maintain and manage volumes of data storage within a datastorage system suffer from a number of deficiencies. Embodiments of thepresent invention are based, in part, on the recognition of thesedeficiencies and provide solutions to overcome them. The techniques ofthe invention also go beyond solving problems of prior art systems andprovide unique mechanisms related to volumes within data storage systemsthat provide significant advancements in the state-of-the art.

Prior art data storage systems provide volume interfaces which arestatic in configuration. Once a volume is configured, its association tospecific storage devices within the data storage system cannot changeunless the volume is reconfigured. As noted above, reconfiguration mustbe performed while the prior art volume is in an off-line state withrespect to host computing devices. Moreover, a systems administratormust reboot the operating systems on most host computing devices thatrequire access to a newly configured volume, which results insignificant overhead and lost processing time.

Prior art volumes provided by conventional data storage systems are alsostatic in storage size. The storage size or total amount of data storagecapacity within a prior art volume is directly dependant upon how muchstorage space is present within the storage devices (or portionsthereof) that are associated with the prior art volume at volumeconfiguration time. The concepts of storage size and actual storagespace associated with a prior art volume are essentially one in the samein prior art data storage systems. That is, the process of associatingstorage devices to the volume during volume configuration inherentlydetermines the storage size of a volume based upon the actual amount ofstorage space associated with the volume. The storage size of a volumecannot be configured separately or changed independently of theassociated storage space. For example, one generally cannot separatelyassociate some storage devices to a volume and then arbitrarily select asize for that volume which is different that the actual amount of spacewithin the associated storage devices. Thus, the storage size of avolume as seen by a host is the actual amount of storage space providedby that volume. Also, prior art volumes cannot exist in a data storagesystem without some minimum amount of storage space associated with thevolume. In other words, prior art volumes with a size of zero cannotexist in a conventional data storage system.

Another deficiency of conventional data storage systems is that thesesystems do not provide adequate support for multiple hosts to access thesame volume in many circumstances. For example, two different hostsarchitectures that use different operating systems that try, forexample, to directly connect to the same data storage system and mountthe same volume of data storage can frequently experience problems dueto incompatibilities between host-specific access information, such asthat stored in Block 0, as required by each host. Since each differentoperating system attempts to maintain its own host-specific accessinformation in Block 0 of the volume, the two disjoint hostarchitectures can experience difficulties when each attempts to decipherthe host-specific access information created by the other host.

Due to the aforementioned examples of deficiencies with prior art datastorage systems, certain other problems may be encountered when hostcomputing device software applications and operating systems attempt tointeract with prior art volumes in various circumstances. For instance,data storage applications that create and continuously maintain a mirrorimage volume of a master volume can experience problems when the mirrorimage volume is taken “off-line” for backup or testing purposes. This isfrequently the case, for example, when using the Windows NT operatingsystem on a host. Certain mechanisms within Windows NT periodicallyattempt to access or “touch” all volumes that are “visible” or that areknown to exist to Windows NT. When using the mirroring application, themirror image volume can be periodically become “visible” and “invisible”to the host as the mirror image volume is taken offline for backup ortesting purposes. When this occurs, Windows NT may experience a faultsince the volume is no longer visible to the operating system when theoperating system performs its periodic volume access or touch. If afault does not occur when the mirroring application removes the volumefrom the host, when the operating systems performs a subsequent periodicaccess or touch, the operating system may reset the number of “visible”volumes that are apparent to Windows NT. However, when the mirroringapplication subsequently reattaches the mirror image volume to the hostin order to re-synchronize data with the master volume, the appearanceof the unknown mirror image volume (without rebooting Windows NT) maycause Windows NT to experience difficulties.

Other problems are presented when prior art volumes are used withsoftware applications as well. For example, certain softwareapplications have requirements for certain minimum volumes sizes inorder to operate properly. These applications may encounter difficultiesif a prior art volume is pre-configured to a static size that becomestoo small for future use. In a database application, for example, if asystems administrator configures a prior art volume with ten gigabytesof storage device space, and the database application later requiresfifteen gigabytes within the volume, the systems administrator mustreconfigure the ten gigabyte volume to contain more associated storage.Not only is volume reconfiguration cumbersome for the reasons notedabove, but the systems administrator must purchase or otherwise obtainthe additional five gigabytes of storage device space.

Many of the problems experienced by applications and operating systemsthat interact with prior art data storage systems and volumes stem inpart from the fact that prior art volumes only exist when theconfiguration process allocates storage device space to the volume. Thatis, a prior art volume is essentially equivalent to, and un-attachablefrom, the storage space associated with the volume. Thus, in the aboveexample of the mirroring application, if the mirror volume's storage isrequired elsewhere (e.g. for use in testing on another host system),when the mirroring application removes the mirror image volume from themaster host system making it no longer “visible” from the perception ofthe master host operating system, the master host operating system maycrash.

The present invention provides an alternative to prior art data storagesystems and volume creation and management techniques and solves many ofthe deficiencies found in such systems. To do so, the present inventionspecifically provides a system and method within a data storage systemthat provide an interface to a data storage system. The interface of theinvention is called a volume in this description. To provide theinterface, the system defines a volume within the data storage system.The volume can have an associated identifier. The system creates thevolume when there are storage devices associated with the volume, andwhen there are no storage devices associated with the volume. The systemprovides the volume as a volume of available data storage to a computingdevice which is external to the data storage system. The volume ofstorage is accessible with the associated identifier. In accordance withthe invention, since the volume can exist in the data storage systemeven if no storage devices (i.e., storage space) are associated with thevolume, hosts that interface to the data storage system that require themere existence of a volume can operate effectively.

To define the volume, the system of the invention identifies a number ofstorage devices and associates the identified number of storage deviceswith the volume. The system also selects a storage size for the volume.These two steps are preferably performed independent of each other. Thatis, selecting a storage size for the volume can be done independent ofthe identified number of storage devices associated with the volume.Alternatively, the selected storage size may be dependent on an amountof data storage associated with the identified number of storage devicesassociated with the volume. In yet another alternative configuration,however, the selected storage size for the volume may be independent ofany storage devices associated with the volume. In yet anotherconfiguration, the selected storage size for the volume may be dependentbut different from of an amount of data storage associated with storagedevices associated with the volume. In this manner, the volumes providedby the invention can be perceived by the hosts as having one size, whenin reality, they have a different amount of actual associated storagespace within the data storage system.

A configuration is provided in which there are no storage devicesassociated with the volume and the volume indicates a storage size thatis greater than zero. Another configuration is provided in which thereare no storage devices associated with the volume and the volumeindicates a storage size that is zero. As will be explained, theseconfigurations overcome may of the problems associated with prior artsystems.

In accordance with another configuration of the invention, theassociated identifier of the volume is a persistent identification andthe system provides the volume to as a volume of available data storageand provides access to the volume to a plurality of networked computingdevices, each of which perceives the volume with the persistentidentification.

The system of the invention also provides a dynamic volumereconfiguration process which detects a requirement for a storage deviceto be associated with a volume in the data storage system. The systemcan then determine if the volume contains an association to an identityof the storage device, and if not, the system can dynamically create, inthe volume, an association to the identity of the storage device thuscausing the storage device to be accessible via the volume. The systemthen provides access to the storage device through the volume. Thisallows storage space to be added to the volume when needed. Forinstance, in another configuration, when the system detects arequirement for a storage device, this process is initiated by anattempted access to a requested storage device understood by a computingdevice to be associated with the volume. Thus, as hosts access volumesof this invention, space can be dynamically added to the volumes on anas-needed basis.

Alternatively, the process of detecting a requirement for a storagedevice in a volume may be initiated by detecting a presence of athreshold amount of occupied storage associated with the volume. Inanother alternative configuration, process of detecting a requirementfor a storage device is initiated by detecting a trend in an amount ofstorage use associated with the volume.

The dynamic reconfiguration process can also remove storage space from avolume. To do so, embodiments of the invention can detect a requirement,for a non-required storage device that has an existing association withthe volume, to no longer be associated with the volume in the datastorage system. The system can dynamically remove, from the volume, theassociation to the identity of the non-required storage device in thedata storage system, thus de-allocating the non-required storage devicefrom the volume while continually providing the volume as a volume ofavailable data storage in the data storage device. This allows thede-allocated storage space to be used for other purposes, such as backupor testing.

In accordance with one embodiment, the process of dynamically removingmaintains a storage size associated with the volume that is the samebefore and after removal of the association of the identity of thenon-required storage device from the volume.

Another embodiment of the invention provides a systems that allowsaccess to data by multiple computing devices through a volume in a datastorage system. The system can receive an access request to the volumeby a computing device and can retrieve access information within thevolume that is specific to the computing device requesting access to thevolume. Then, the system can provide, to the computing device, theaccess information to allow the computing device to properly access thevolume. This allows multiple hosts to access the volume, even thougheach may have different access information.

In a more particular configuration, the system determines if the volumecontains volume information that is different from volume informationcontained within the access information, and if so, replaces, within theaccess information, the volume information that is different with thevolume information from the volume. This allows the volumes provided bya data storage system in accordance with the invention to provideconsistent volume information to a host computing device, even if thehost computing device attempts to use information within itshost-specific access information to determine volume characteristics.

As an example, in one configuration, if the volume information that isdifferent is storage size information in the volume to which access isrequested, the storage size information contained within the accessinformation provided to the computing device is storage size informationobtained from the volume instead of actual storage size informationrelated to storage devices associated with the volume.

In other embodiments of the invention, wherein the computing devices mayoperate using different architectures, the process of retrieving accessinformation determines an identity of the computing device attempting toaccess the volume and retrieves architecture specific access informationfor the volume for that computing device from the volume based on theidentity of the computing device. In a variation of this configuration,the different architectures can be different operating systems whichexecute on the computing devices. In this case, the system of theinvention provides to the computing device the architecture specificaccess information including operating system block organizationinformation relating to how the operating system of the computing devicestores blocks of data in storage devices associated with the volume. Inthese embodiments, the access information may be specific for each ofthe plurality of computing devices.

Other embodiments of the invention provide a data storage system thatincludes a host interface capable of coupling to at least one computingdevice. Also included is a storage device interface capable of couplingto one or more storage devices maintained within the data storagesystem. A memory is coupled to the host interface and the storage deviceinterface. The memory contains a volume which can have an associatedidentifier. The volume exists in the memory as an accessible volume foraccess by computing devices via the host interface. The volume existswhen there are storage devices associated with the volume, and whenthere are no storage devices associated with the volume. As explainedabove, this aspect of the invention allows volume to exist which may uselittle or no storage in the data storage system.

The volume in the memory may include storage size indicating anavailable amount of data storage associated with the volume. The storagesize can contain a value that is programmable and is dependant, butdifferent than a size of any storage devices associated with the volumevia the storage device interface.

The data storage system can also include at least one storage devicecoupled to the storage device interface. In this configuration, thestorage device can have a portion associated with the volume. Theportion can have an actual size and the volume in the memory includes astorage size indicating an available amount of data storage associatedwith the volume. The storage size may contain a value that is not equalto the actual size of the portion of the at least one storage deviceassociated with the volume. In this manner, the actual amount of storagespace associated with the volume is not that same as that indicated bythe storage size of the volume presented to host computing devices.

Also in the data storage system in this invention, the associatedidentifier of the volume may be a persistent identification containing avalue unique to the volume. In this case, the host interface includes ameans for providing the volume as a volume of available data storage toa plurality of networked computing devices. Each of the networkedcomputing devices perceives the volume with the persistentidentification that is the same. This configuration allows the datastorage system to be accessed by separate hosts using identifiers thatare the same for the same volumes.

The data storage system also contains a means for detecting arequirement for a required storage device to be associated with thevolume in the data storage system and a means for determining if thevolume contains an association to an identity of the required storagedevice through the storage device interface. If no association ispresent, a means is provided for dynamically creating, in the volume, anassociation to the identity of the required storage device through thestorage device interface, thus causing the required storage device to beallocated to the volume. Also, a means is provided for providing accessto the required storage device through the volume using the hostinterface.

Also in this configuration, the data storage system can further includea means for detecting a requirement, of a non-required storage devicethat has an existing association with the volume through the storagedevice interface, to no longer be associated with the volume in the datastorage system. Further provided in this configuration is a means fordynamically removing, from the volume, the association to the identityof the non-required storage device through the storage device interfacein the data storage system, thus de-allocating the non-required storagedevice from the volume while the volume continually appears, via thehost interface, as a volume of available data storage having anunchanging storage size in the data storage system. This configurationallows storage space to be added and removed as needed to and from thevolume without disturbing host interaction with the volume.

In another configuration of the data storage system, the memory iscoupled to the host interface and the storage device interface and thememory contains a volume. The volume contains a plurality of sets ofaccess information allowing a plurality of specific computing devices toaccess data stored on the at least one storage device according to the aparticular arrangement associated to each of the plurality of computingdevices. Also provided is a means for storing access information for atleast one storage device. The access information is specific for each ofa plurality of computing devices that can access the at least onestorage device. This configuration allows different host operatingsystems to directly interface and simultaneously access the same volume,since the access information required for each host is maintained foreach storage device within the volume.

A specific computing device can interface, for example, via the hostinterface, with the data storage system. A label manager is provided inthis configuration and is coupled to the host interface and to thememory. The label manager receives, via the host interface, an accessrequest from the specific computing device to the volume in the memory.The label manager can retrieve one of the sets of access informationwithin the volume that is associated with the specific computing devicerequesting access to the volume and can provide, to the specificcomputing device, the retrieved set of access information to allow thespecific computing device to properly access the volume.

Also included in this label manager configuration is a means fordetermining if the volume contains volume information that is differentfrom volume information contained within the retrieved set of accessinformation, and if so, a means is provided for replacing, within theretrieved set of access information that is provided to the specificcomputing device, the volume information that is different with thevolume information from the volume. This allows the volumes provided bythe invention to present consistent information to host computingdevices, even if those hosts have their own information relating tovolume parameters that might be different than that maintained withinthe volume in the data storage system.

For instance, in one configuration, the storage size informationcontained within the set of access information provided to the specificcomputing device is storage size information obtained from the volume,instead of actual storage size information related to storage devicesassociated with the volume.

The different access information is provided to accommodate differenthost operating systems and architectures that require access to the samevolume. As such, a configuration of the invention is provided thatincludes a means for determining an identity of the specific computingdevice attempting to access the volume. Also, a means is provided forretrieving, from the volume, architecture specific access informationassociated with a storage device having an association with the volumefor that specific computing device based on the identity of the specificcomputing device. More specifically, if the different architectures aredifferent operating systems, the label manager further comprises a meansfor providing, to the specific computing device, the architecturespecific access information which can include operating system blockorganization information relating to how an operating system of thespecific computing device stores blocks of data associated with thestorage device having an association with the volume for that specificcomputing device.

The data storage system can also include a means for determining if thevolume to which access is requested contains an association to anidentity of a required storage device that is associated with the accessinformation provided to the specific computing device, and if not, candynamically create, in the volume to which access is requested, anassociation to the identity of the required storage device thus causingthe required storage device to be allocated to the volume. The abovemeans are preferably provided by a programmed microprocessor within thedata storage system and the volumes of the invention are preferablymaintained in a channel director.

In another embodiment of the invention, a method provides a volumeinterface to a data storage system. The method includes the steps ofreceiving a request from a computing device for a volume in the datastorage system and providing, from the data storage system to thecomputing device, in response to the request, a volume that satisfiesthe request when there are storage devices associated with the volume,and when there are no storage devices associated with the volume.

Embodiments of the invention are also provided that consist of computerprograms encoded onto computer readable mediums, such as memory devices,disks, and so forth. Preferably, these embodiments are in the form of acomputer program product having a computer-readable medium includingcomputer program logic encoded thereon. The computer program code allowsa data storage system to provide an interface to the data storage systemas explained herein, when the computer program logic is executed on atleast one processing unit with the data storage system. The computerprogram product is preferably a hard disk, floppy disk, optical orCD-ROM disk, or other computer-readable media. Such a disk encoded withinstructions that perform any of the methods of the invention asexplained herein is itself considered an embodiment of the invention.

Thus, a computer readable medium such as a disk or Read Only Memory(ROM) or Random Access Memory (RAM) chip, that is separate from a datastorage system, but that is encoded with computer program instructions,that, if compiled and executed, or just executed on processor within adata storage system, would cause the data storage system to create,maintain, and manipulate the volumes of the invention, and/or wouldotherwise operate using the inventive techniques described herein, is tobe understood to be an article of manufacture and is considered anembodiment of this invention. The disk, memory, or medium need not beloaded or installed on any data storage system, processor, host or othercomputing device, but may simply exist alone as contain the encodedcomputer software code that provides the aforementioned operations. Thesoftware to carry out these instruction may be written in any type ofcomputer code, including such languages as C, C++, Java, assemblylanguage, or a proprietary language, and so forth, or may exist ascomplied object code ready for execution by a processor.

An example embodiment of a data storage system configured according tothe invention is any one of the Symmetrix data storage systemsmanufactured by EMC Corporation of Hopkinton, Mass. Symmetrix is aregistered trademark of EMC Corporation.

BRIEF DESCRIPTION OF THE DRAWINGS

The foregoing and other objects, features and advantages of theinvention will be apparent from the following more particulardescription of preferred embodiments of the invention, as illustrated inthe accompanying drawings in which like reference characters refer tothe same parts throughout the different views. The drawings are notnecessarily to scale, with emphasis instead being placed uponillustrating the embodiments, principles and concepts of the invention.

FIG. 1 is an example of a data storage system illustrating exampleconfigurations of volumes configured according to the invention.

FIG. 2 illustrates a more detailed view of a channel director within adata storage system that contains volume interfaces configured accordingto various example embodiments of the invention.

FIG. 3 is a flow chart of the processing steps used to create a volumewithin a data storage system according to one embodiment of theinvention.

FIG. 4 is a flow chart of the processing steps used to dynamicallyreconfigure a volume to allow more storage space to be associated withthe volume according to one embodiment of the invention.

FIG. 5 is a flow chart of the processing steps used to dynamicallyreconfigure a volume to remove or disassociate storage space from thevolume according to one embodiment of the invention.

FIG. 6 illustrates an exchange of information between multiple hostcomputing devices, a switch, and a data storage system which allows themultiple hosts to each access a single volume according to oneembodiment of the invention.

FIG. 7 is a more detailed illustration of a volume configured accordingto an example embodiment of the invention that allows multiple hosts toaccess data within storage devices associated with the volume.

FIG. 8 is a flow chart of the processing steps performed to allow avolume to provide access by multiple hosts to data stored within thevolume according to one embodiment of the invention.

FIG. 9 is a block diagram illustrating how a persistent identificationprovided by a volume configured according to this invention can be usedto allow the volume to reference data storage devices that arephysically located in another data storage system.

DETAILED DESCRIPTION OF PREFERRED EMBODIMENTS

FIG. 1 illustrates an example embodiment of a data storage system 100-1configured according to the invention. The data storage system 100-1includes a plurality of storage devices 114 through 116 which, in thisexample, specifically include three two-gigabyte disk drives 114-1through 114-3 (collectively 114), three four-gigabyte disk drives 115-1through 115-3 (collectively 115), and three tape drives 116-1 through116-3 (collectively 116). The storage devices 114 through 116 providephysical or “raw” data storage which maintains data in a binary formatwithin the data storage system 100-1.

Each storage device 114 through 116 interfaces with a disk or tape(disk/tape) director 104. A system bus 108 interconnects the disk/tapedirector 104 to a cache memory 103, a processor 106, and a channeldirector 102. The channel director 102, as will be explained, providesthe hardware and software interfaces which allow connections 156 through158 from the host computing devices 150 through 152 to access (readand/or write) data within the data storage system 100-1. A remoteinterface 105 interconnects with the disk/tape director 104, theprocessor 106 and the channel director 102, and provides a mechanism 107for interfacing the data storage system 100-1 to one or more other datastorage systems (not shown in this figure).

FIG. 1 illustrates a plurality of volumes 110 through 112 within thechannel director 102, as well as a “standard” volume 113. The volumes110 through 112 operate according to embodiments of the invention asexplained herein, while the standard volume 113 operates in aconventional manner. It is to be understood that a data storage system(e.g., 100-1) configured according to embodiments of the invention mayinclude both standard volumes (e.g., 113) and volumes (e.g., 110 through112) of the invention, or may use only volumes of the invention (e.g.,110 through 112) and the techniques described herein exclusively. Thestandard volume 113 is not required for a data storage system configuredaccording to the invention and is only provided to illustrate thedifferences between volumes of the invention (e.g. 110 through 112) andstandard volumes (e.g. 113).

The terms “volume” refers to a volume configured according toembodiments of the invention. However, when prefaced with the term“standard”, the phrase “standard volume” is specifically used herein toreference techniques associated with conventional volumes of datastorage. As noted above, the standard volume 113 is provided in thisexample only to highlight distinctions between the volumes provided in adata storage system configured according to the invention as compared tostandard volume implementations. Generally, both the standard volume 113and the volumes 110 through 112 allow host computing devices 150 through151 to interface with the data storage system 100-1 to access datamaintained on the storage devices 114 through 116.

FIG. 1 illustrates certain aspects of the invention in comparison toconventional data storage system access techniques. A high leveloverview of the system and methods of the invention will now bepresented to allow the reader to better understand and appreciate moredetailed aspects of the invention, which are presented later.

Typically, a systems administrator (not shown) establishes the standardand volumes 110 through 113 during an initial setup and configurationprocess that is performed when the data storage system 100-1 is coupledto one of host computing devices 150 through 152. A software applicationprovided within the operating system (not specifically shown) on thehost 150 through 152 that couples to the data storage system 100-1 canbe used to perform volume configuration. Alternatively, a softwareapplication designed to specifically operate and manage the data storagesystem 100-1 can be used to configure the volumes 110 through 113.

The systems administrator configures the standard volume 113 by creatinga standard volume 113 (SV1) within the channel director 102 andassociating one or more storage devices 114 through 116 (or portionsand/or combinations thereof) to the standard volume 113. The associationindicates which storage devices 114 through 116 are to provide thephysical data storage for the standard volume 113. The amount of storagespace within storage devices 114 through 116 that are associated withthe standard volume 113 during configuration inherently defines astorage size (not specifically shown in this figure) of the standardvolume 113. There must be at least some amount of storage space (i.e.,at least a portion one of storage devices 114 through 116) associatedwith the standard volume 113 in order for the configuration process tocreate a standard volume 113 in the channel director 102. Onceconfigured, the standard volume 113 has a fixed storage size that isequal to the amount of storage space within the storage devices 114through 116 that the systems administrator associated with the standardvolume 113.

A host computing device (i.e., one of hosts 150 through 152) that isused to configure the standard volume 113 is the generally the same hostthat mounts the standard volume 113 once the standard volume 113 isdefined. For instance, if the host 150 configures the standard volume113 with an association to one or more portions of storage devices 114through 116, then that host 150 subsequently mounts the standard volume113. This is because configuration of the standard volume 113 entailswriting certain host-specific access information to a designatedportion, such as Block 0 (not shown in this figure), of the standardvolume 113. The host-specific access information in Block 0 is generallyunique to the architecture or the version of the operating system usedby the host 150. In order for another host 151 and/or 152 to interfacedirectly to the standard volume 113, the host-specific accessinformation within block 0 of the standard volume 113 must be the sameas that required by the other host attempting access. Once the standardvolume 113 is mounted to the host 150, software applications (not shown)that execute on the host 150 can read and write data to the storagespace in storage devices 114 through 116 that are associated with thestandard volume 113.

To increase or decrease the amount of storage space associated with thestandard volume 113, a systems administrator must disable access to thestandard volume 113 from any applications and/or users on the hostcomputing device (one of 150 through 152) that mounts the standardvolume 113. Essentially, the standard volume 113 is brought off-linewhile it is reconfigured with a different association of portions ofstorage devices 114 through 116. After the standard volume 113 isreconfigured with more or less storage space, a host (one of 150 through152) that requires access the newly configured standard volume 113 mustbe rebooted in order to for the host to re-detect the standard volume113 within the data storage system 100-1.

In this manner, the standard volume 113 provides an interface to acertain static amount of data storage space within the storage devices114 through 116 in the data storage system 100-1 for one of the hosts150 through 152. The actual amount of storage space is fixed in sizeonce the standard volume 113 is configured and governs the storage sizeof the standard volume 113. Changing the amount of storage space in astandard volume 113 requires an offline reconfiguration process and hostcomputing devices 150 through 152 must be rebooted to detect thereconfigured standard volume 113. Moreover, access to the standardvolume 113 is generally only available to hosts 150 through 152 thathave the same operating system and that use the same host-specificaccess information maintained within a designated portion of thestandard volume 113.

The volumes 110 through 112 are created by a configuration process (tobe explained) provided by the invention. However, in contrast to thestandard volume 113, which requires some amount of associated storagespace and which has a storage size defined exactly by that associatedamount of storage space, according to this invention, the volumes 110through 112 are not required to have an association to any portions ofstorage space within storage devices 114 through 116 (though they may)in order to exist in the channel director 102. That is, theconfiguration process of the invention can create the volumes 110through 112 as virtual interfaces to the data storage system 100-1 thatare visible to the host computing devices 150 through 152, but that neednot have any actual associated amount of storage space assigned orassociated to them within the data storage system 100-1.

Another aspect of the volumes 110 through 112 of this invention is thatthey can have an arbitrary storage size (not specifically shown in FIG.1). The configuration process of the invention allows independentselection or setting of the storage size for a volume 110 through 112.Moreover, the storage size does not require any relationship (though itmay have such a relationship) to any portions of storage devices 114through 116 that may (or may not) be associated with the volumes 110through 112. By way of example, the initial configuration process can beused to set the storage size for a volume 110 through 112 to tengigabytes, while the actual amount of total data storage within storagedevices 114 through 116 that is allocated to, or associated with, thevolume 110 may only be five gigabytes, or even zero gigabytes (i.e. nodata associated data storage associated with the volume). The techniquesof the invention allow the volumes 110 through 112 to exist in thechannel director 102, even though there may be no storage spaceassociated with the volumes 110 through 112.

Also, unlike the standard volume 113, as applications executing on thehost computing devices 150 through 152 begin to utilize more and morestorage space associated with mobiles volume 110 through 112, accordingto this invention, a dynamic reconfiguration process provided by theinvention can be used to reconfigure the volumes 110 through 112 inreal-time (as will be explained with respect to FIGS. 4 and 5) to haveassociations with more or less actual storage space within the storagedevices 114 through 116. The dynamic reconfiguration process for avolume 110 through 112 can performed volume reconfiguration withoutrequiring the volume to go offline from the perspective of hosts 150through 152, as is the case when prior art reconfiguration process areused to reconfigure the standard volume 113. That is, the data storagesystem 100-1 can perform a dynamic reconfiguration process automaticallywithout disturbing the interfaces 156 through 158 between the volumes110 through 112 and the host computing devices 150 through 152. Asystems administrator does not need to isolate or take off-line the datastorage system 100-1 and/or the volumes 110 through 112 from the hosts150 through 152 during the dynamic reconfiguration process of theinvention. The dynamic reconfiguration process can also take placeautomatically in response to various triggering events. Furthermore,there is no need to restart the host computing devices 150 through 152in order to detect the reconfigured volumes 110 through 112.

According to another technique of the invention, multiple host computingdevices 150 through 152 using different operating systems cansimultaneously interface with a single volume (i.e. one of 110, 111 or112). Generally, as will be discussed in more detail, the volumes 110through 112 can maintain separate host-specific access information (notshown) for each host computing device 150 through 152. By storing thehost-specific access information for multiple hosts 150 through 152, avolume 110 through 112 can present the proper access informationspecifically required by the operating system on a host computing device150 through 152 that requests access to the volumes 110 through 112.

FIG. 2 provides a more detailed illustration of the channel director 102including the standard volume 113, and the volumes 110 through 112within the data storage system 100-1, as configured according to variousembodiments of the invention. The different configurations of thevolumes 110 through 112 in FIG. 2 demonstrate some of thecharacteristics of embodiments of the invention that were previouslydiscussed at a high-level with respect to FIG. 1.

In this example, each volume 110 through 112 is illustrated as a datastructure within the channel director 102, which may be a programmablememory device, for example. Each volume 110 through 112 includes astorage size 124, an associated identifier 122, a plurality of storagedevice interfaces 120 (three in this example—120-1 through 120-2), alabel manager 130 (abbreviated LM in this figure), and a remoteinterface 126. Each volume 110 through 112 is respectively labeledVOLUME 1, VOLUME 2 AND VOLUME 3 in contrast to the standard volume 113which is labeled STANDARD VOLUME 1.

The standard volume 113 includes device interfaces 117-1, 117-2 and117-3, each of which in this example has two gigabytes of associatedstorage space within one or more of the storage devices 114 through 116(FIG. 1). The standard volume 113 also includes a storage size 119,which is equal to six gigabytes in this example. As represented byinterface 107, the storage size 119 of the standard volume 113 iscompletely dependent on how much total storage space (i.e., withinstorage devices 114 through 116) is associated with the standard volume113 via the interfaces 117. In other words, the six gigabyte storagesize 119 in this example is a cumulative sum of all of the storage spacereferenced by interfaces 117 within any of the storage devices 114through 116. During configuration of the standard volume 113, the systemadministrator does not set the storage size 119. Rather, the systemsadministrator simply associates a certain amount of storage space withinthe storage devices 114 through 116 to the standard volume 113 viainterfaces 117. The amount of storage space referenced by the interfaces117 thus determines the value of the storage size 119 of the standardvolume 113. A standard volume must have some storage space referenced byat least one of the interfaces 117 in order for the standard volume 113to exist within the channel director 102.

The three volume entries 110 through 112 in this example illustrationare each configured according to various embodiments of the invention.None of the illustrated configurations of volume entries 110 through 112can be achieved using prior art or standard volume techniques, such asthose discussed with respect to standard volume 113.

Volume 110 illustrates an embodiment of the invention in which thestorage size 124-1 is different in value from the actual amount ofstorage space within storage devices 114 through 116 referenced viainterfaces 120-1 through 120-3. As illustrated, each interface 120-1through 120-3 is associated with a two gigabyte disk 114-1 through114-3, respectively, for a total amount of six gigabytes of actualstorage space that is associated with the volume 110. However, aspresently configured, the storage size 124-1 indicates a value of thirtygigabytes of available data storage. The storage size 124-1 having thethirty gigabyte value is provided to any hosts 150 through 152 thatattempt to access the volume 110. Accordingly, the volume 110 providesthe appearance to the hosts 150 through 152 that it has thirty gigabytesof data storage available, when in reality, only a total of sixgigabytes from data storage devices 114 through 116 are actuallyassociated with the volume 110.

The disparity between the actual amount of data storage devices 114through 116 that are associated with the volume 110 via interfaces andthe storage size 124-1 that is presented externally to hosts 150 through152 is made possible in the invention by allowing the storage size 124-1to be set or selected during volume configuration independently of theassociation process of storage devices 114 through 116 for the volume110.

By presenting a storage size 124-1 that may be different than an actualamount of storage space associated with the volume 110, this embodimentof the invention allows applications on host computing devices 150through 152 that require minimum amounts of storage space in a volume toexecute properly without actually initially committing (i.e.associating) the required minimum amount of storage space to the volume110 within the data storage system 100-1. The invention also allows thevolume 110 to associate more actual storage space within storage devices114 through 116 to the volume 110 as the actual amount of storage (thesix gigabytes referenced via interfaces 120-1 through 120-3 in thisexample) begins to be fully utilized or consumed with data from anapplication executing on the hosts 150 through 152. The association ofadditional storage space to the volume 110 can be performed withoutinterrupting either the application on the hosts 150 through 152, or theinterfaces 156 through 158 between the hosts 150 through 152 and thedata storage system 100-1.

The volume 111 in FIG. 2 illustrates another configuration of a volumeaccording to an embodiment of the invention. In the volume 111, thestorage size 124-2 indicates to the hosts 150 through 152 that twentygigabytes of data storage is available. However, as presentlyconfigured, the data storage device interfaces 120-4 through 120-6 inthe volume 111 are not associated with any portions of the storagedevices 114 through 116.

The volume 111 thus presents itself to the external hosts 150 through152 as a twenty gigabyte volume of data storage, when in reality, nostorage is currently allocated to or available within the volume 111.Again, this configuration is made possible in the invention by allowingthe storage size 124-2 of the volume 111 to be configured independentlyof any association that may or may not exist (the later in thisexample), to storage space within the storage devices 114 through 116.

The volume 111 is useful in situations where an application thatexecutes on one or more of the host computing devices 150 through 152requires that a volume have a minimum size. In other words, volume 111is useful when a volume of a certain size that is greater than zeromerely needs to be “visible” to the hosts 150 through 152. The inventionprovides a mechanism to detect when a data access to the volume 111 isrequired and allows the data storage system 100-1 to associate storagespace with the volume 111 on-the-fly so that the data access can becarried out.

The volume 112 in FIG. 2 illustrates yet another example configurationof an embodiment of the invention. The volume 112 is configured to havea storage size 124-3 that contains a value of zero and also has noportions of storage devices 114 through 116 associated with the datastorage device interfaces 120-7 through 120-9. The volume 112 is usefulin situations where an application on one or more of the hosts 150through 152 requires that a volume simply be present or visible to thehost and that the host or application does not, at that time, actuallyrequire read or write access to any data in the volume.

An example use of volume 112, which has a size of zero (124-1) and noassociated storage space, is when a data-backup application exists on ahost 150 and is responsible for periodically backing up all of the datastorage devices 114 through 116 to a tape backup device (not shown)which is external to the data storage system 100-1. During periods whenthe data-backup application is not in use, the volume 112 can have allassociated storage space removed (as illustrated by interfaces 120-7through 120-9 which reference NULL) and can have its storage size 124-3set to zero. Since the storage size 124-3 is zero, no applications onthe hosts 150 through 152 will attempt to mount and/or access datawithin the volume 112. The volume 112, however, which is only usedduring backups, never “disappears” from the “view” of the hosts 150through 152, and thus does not require the hosts 150 through 152 to berebooted in order to detect a special volume used only for backing updata.

During periods when backup operations are underway, the volume 112 canbe used as the backup volume and can have associations with variousamounts of storage space within storage device 114 through 116 createdas needed via interfaces 120-7 through 120-9. The backup application canwork in conjunction with the data storage system 100-1 to cyclicallyassociate portions of storage space from storage devices 114 through 116to the volume 112, then backup those portion to tape, and thendisassociate those portions and move on to associate another portion ofstorage space to the volume 112. This process can be repeated using thevolume 112 as the backup focal point until all of the data in the datastorage system 100-1 is archived.

The configurations of volumes 110 through 112 in FIG. 2 are illustratedas examples only, and are not limiting of the invention. As such, it isto be understood that other configurations of volumes can exist as wellthat are within the scope of this invention. For example, embodiments ofthe data storage system 100-1 may exist that provide a volume that has astorage size 124 that is dependent in some manner, but different from anactual amount of data storage associated with the storage devices 114through 116 that are associated with the volume 110 through 112.Specifically, an example embodiment might provide a storage size 124that is always five gigabytes more than the actual amount of datastorage associated with the volume via interfaces 120. In this case, thestorage size 124 selected at volume configuration time is dependent, butdifferent, from the amount of data storage associated with theidentified storage devices 114 through 116 that are associated with thevolume 110 through 112.

In an alternative arrangement, the storage size 124 of a volume 110through 112 can indicate a value that is less than the actual amount ofstorage space within devices 114 through 116 that is associated with thevolume 110 through 112. By way of example, the storage size 124 of avolume (one of 110 through 112) may indicate eight gigabytes ofavailable data storage, when in actuality, ten gigabytes are associatedwith the volume 110. Such a configuration is valuable in cases, forexample, where an application on hosts 150 through 152 accidentallyattempts to write an amount of data, such as nine gigabytes, to a volumeconfigured in such a manner. In this case, the amount of data to bewritten exceeds the eight gigabyte value maintained within storage size124, but is less than the ten gigabytes of associated storage spacewithin storage devices 114 through 116. As such, the nine gigabytes ofdata is successfully written to the storage space associated with thevolume 110, the successful write operation is reported back to the hostsoriginating the write request. At that point, the dynamicreconfiguration process of the invention can be used to associate morestorage space within storage devices 114 through 116 to the volume. Inessence, this configuration acts as overflow protection in attempts towrite too much data to a volume.

FIG. 3 shows the processing steps 301 through 307 that are performedaccording to one embodiment of the invention to create a volume within achannel director 102, such as volume 110 within the data storage system100-1. Steps 301 through 307 are typically performed by data storagesystem configuration software executing as part of, or in conjunctionwith the operating system of a host computing device (i.e. one of 150through 152) that interfaces with the data storage system 100-1.Alternatively, the data storage system 100-1 may include its owninternal software configuration program accessed via a direct systemsadministrator console which is provided as part of the data storagesystem 100-1. The processor 106 may execute the instructions shown inany of the flow charts in this description in order to manipulate thechannel director 102. Alternatively, the channel director 102 itself mayinclude circuitry to process these instructions.

Processing begins at step 301 by defining a volume 110 in memory withinthe data storage system 100-1. Preferably, the memory is part of thechannel director 102. Next, in step 302, a value for the volumeidentifier 122 (FIG. 2) is selected (or set) and associated with thevolume 110. In step 303, a value for the storage size 124 is selectedfor the volume 110. The storage size 124 set in step 303 can be anyvalue, including zero.

After the volume (e.g. 110) is created (step 301) and has valuesassigned to the an identifier (i.e., 122, step 302) and a storage size(i.e., 124, step 303), a volume now exists in the channel director 102.The volumes 110 through 112 can exist when there are storage devices 114through 116 associated with the volume entries, and even when there areno storage devices 114 through 116 associated with the volume entries.Next, in step 304, any storage devices 114 through 116 that are to beassociated with the volume 110 are selected. In step 305, the processingdetermines if any portions of any storage devices 114 through 116 wereselected for association with the volume 110. If so, processing proceedsto step 306 where the selected portions (from step 304) of the storagedevices 114 through 116 are associated with the volume 110. Step 306essentially establishes the pointers 131, as needed, from interfaces 120to the selected storage devices 114 through 116. If an interface 120 isnot used, it is set to a NULL value, indicating that no storage space isassociated with that interface 120.

After step 306 is complete, or, if no storage devices 114 through 116were selected (step 304) to be associated with the volume, processingproceeds to step 307, at which point the volume is provided as a volumeof available data storage to host computing devices 150 through 152.

The volumes 110 through 112 are preferably accessible via the associatedidentifier stored in location 122. Since the storage size 124 for avolume 110 through 112 is configured in step 303 independently of anystorage devices 114 through 116 that are to be associated with thevolume, any of the volume configurations 110 through 112 discussed abovewith respect to FIG. 2 are possible as a result of the processing inFIG. 3. Once a volume 110 through 112 is configured according to steps301 through 307, it can be accessed as a regular volume of data storageby any of the hosts 150 through 152. As will be explained next, ifstorage space needs to be added or removed from a volume configuredaccording to the steps in FIG. 3, a dynamic reconfiguration process isused which allows host computing devices 150 through 152 to remaininterfaced with the volumes 110 through 112 during reconfiguration.

FIG. 4 shows the processing steps 351 through 355 that allow a volume110 through 112 of the invention to dynamically be reconfiguredaccording to the invention. The dynamic reconfiguration process of FIG.4 allows the actual amount of storage space that is associated with avolume 110 through 112 to be altered while the interfaces 156 through158 (FIG. 1) to host computing devices 150 through 152 remain intact.That is, the hosts 150 through 152 continually perceive that the volumeexists before, during and after dynamic volume reconfiguration accordingto step 351 through 355. There is no need to unmount a volume 110through 112 from a host 150 through 152 during reconfiguration, nor isthere a need to reboot the host(s) 150 through 152 or bring them intoany special operating mode, such as single user mode.

Generally, the operation of steps 351 through 355 in FIG. 4 may beprompted by a need to reconfigure a volume 110 through 112 in responseto some stimulus. For example, as illustrated in FIG. 2, the dynamicreconfiguration process of FIG. 4 is invoked if a host 150 through 152attempts to access data within either one of volumes 111 or 112 asconfigured in that illustration. This is because, as illustrated, thereare no actual storage devices 114 through 116 associated with eithervolume 111 or 112, as indicated by the interfaces 120-4 through 120-9referencing NULL values. In these two examples, reconfiguration involvesassociating more storage space (i.e. portions of storage devices 114through 116) to the volumes 111 or 112, though the invention also allowsdynamic reconfiguration in order to remove or disassociate storage spacefrom a volume, as will be explained with respect to FIG. 5.

In step 351, the processing detects a requirement for one or morestorage devices (e.g., 114 through 116) within a volume (e.g., 110through 112). The requirement may be in response to an attempted access(read and/or write) to data within the volume via one of the hosts 150through 152. From the perspective of the host(s) 150 through 152, therequired storage device 114 through 116 may be understood to already beassociated with the volume 110 through 112 to which access is made.Thus, upon the occurrence of step 351, the volume may already have someassociated storage space, such as that illustrated in the configurationof volume 110 in FIG. 2, or no storage space may yet be associated withthe volume, as illustrated in the configurations of volumes 111 and 112,as discussed above.

Step 351 may also be initiated in response to detecting a presence of athreshold amount of occupied storage associated with the volume. Thismay be the case, for example, then the storage size 124 of a volume 110through 112 is always maintained at a greater value than the actualamount of data storage associated with the volume 110 through 112. Assuch, as the total amount of actual storage spaced becomes occupied(i.e., written to), a threshold amount of occupied storage may beexceeded at which point steps 351 through 355 are triggered to add morestorage space to the volume.

Alternatively, step 351 may be triggered by a trend analysis of datastorage usage within the data storage system 100-1. In this case, trendanalysis software in either one or more of the hosts 150 through 152 orin the data storage system 100-1 may determine patterns or periods ofuse requiring various amounts of actual data storage space to beavailable within a volume 110 through 112 during certain time periods.During peak usage periods, the trend analysis software may trigger theinitiation of steps 351 through 355 in order to add or remove (i.e.associate or disassociate) actual data storage to and from the volumes110 through 112.

In any event, after a requirement for a particular storage device 114through 116 (or a portion thereof) is detected for a specific volume 110through 112 in step 351, step 352 then determines if the volume (forwhich the requirement for the storage device is detected in step 351)contains an association to an identity of the required storage device(i.e., an association to the required one of storage devices 114 through116 or portion(s) thereof). That is, step 352 determines if therequested/required storage device is already associated with the volume.This can be done, for example, by determining if any of the storagedevice interfaces 120 currently reference (i.e., are presentlyassociated with) the requested storage device 114 through 116. If thevolume already contains an association to the required storage device114 through 116 specified in step 351, processing proceeds to step 355which provides the volume to the host computing device 150 through 152for access to the requested storage device(s) 114 through 116. In otherwords, step 355 provides access to the required storage device 114through 116 through the volume 110.

If, however, step 352 determines that the volume does not contain anassociation to the identity of the required storage device(s) 114through 116 (from step 351), then processing proceeds to step 353 todetermine the appropriate access information within the volume for therequired storage device(s). Specific processing details of a preferredembodiment of step 353 will be explained in more detail later withrespect to FIGS. 5 and 6. In general, however, step 353 obtains thenecessary access information, which may be host specific, for the host150 through 152 for the storage device 114 through 116 determined to berequired in step 351. In other words, step 353 determines and obtainsthe proper access information allowing the host 150 through 152 toproperly access the requested storage device 114 through 116.

Once the host-specific access information is obtained in step 353, step354 creates, in the volume 110, an association to the identity of therequired storage device 114 through 116. This may be accomplished, forexample, by creating an association from one of the interfaces 120within the volume to the requested storage device 114 through 116. Afterstep 354 is complete, step 355 proceeds to provide the volume to thehost computing device(s) 150 through 152 to allow access to the storagedevice(s) 114 through 116 which are associated with the volume. In thismanner, the data storage system 100-1 can provide dynamicreconfiguration of a volume 110 through 112 to allow storage space to beadded.

While the example processing steps 351 through 355 are explained in thecontext of adding an association to a storage device 114 through 116within one of the volumes 110 through 112, similar processing can beused to remove associations to storage devices 114 through 116 from thevolumes 110 through 112.

FIG. 5 is a flow chart of processing steps 361 through 364 that are usedto dynamically disassociate a storage device 114 through 116 with avolume 110 through 112 according to one embodiment of the invention.

In step 361, the processing detects a requirement for disassociation ofa storage device 114 through 116 that already has an existingassociation with one of the volumes 110 through 112. Step 361 may betriggered, for example, by a process within the data storage system100-1 that detects that a storage device 114 through 116 is about beremoved form the data storage system 100-1 for repair. For each volume110 through 112, step 362 then determines if that volume contains anassociation to the storage device (i.e., one or more of 114 through 116)to be removed. If so, step 363 determines the appropriate accessinformation for the storage device to be removed. As will be explainedshortly, such access information may be host-specific and may specifyhow to properly disassociate a storage device from a volume so as not todisturb the host, depending upon which hosts 150 through 152 areinterfaced (via interfaces 156 through 158 in FIG. 1) to the volume.Once the access information for the storage device is obtained, step 364disassociates the storage device from the volume 110 through 112.

In this manner, the invention is able to remove storage space from avolume 110 through 112 without adjusting or altering the storage size124. Furthermore, the processing of steps 361 through 364 may beperformed while maintaining the interfaces 156 through 158. This allowshosts 150 through 152 to be ignorant of the dynamic reconfigurationprocessing that takes place according to the processing in FIGS. 4 and5.

The aforementioned embodiments of the data storage systems configuredwith the volumes 110 through 112 allow the data storage system 100-1, inconjunction with host computing devices 150 through 150, to overcomemany of the problems associated with prior art volumes. By way ofexample, since the volumes 110 through 112 do not require anyassociation to portions of storage devices 114 through 116 in order toexist as “visible” volume interfaces 156 through 158 within the channeldirector 102, storage space can be added and removed to and from thevolumes 110 through 112 behind-the-scenes within the data storage system100-1. This dynamic allocation of storage space to the volumes 110through 112 can take place unbeknownst to the external host computingdevices 150 through 152. This feature of the invention solves many ofthe problems experienced by prior art operating systems and applicationprograms that experience faults when a volume “appears” and “disappears”within the channel director 102. Since the volumes 110 through 112 canalways remain visible, even though storage devices 114 through 116 canbecome associated and disassociated with the volumes 110 through 112over time, the operating system and applications can continue to operateas normal without faulting.

Moreover, since the volumes 110 through 112 of the invention have astorage size that is independently configurable from any storage devices114 through 116 that may (or may not) be associated with the volumes 110through 112, software applications and operating systems (notspecifically shown) that execute on host computing devices 150 through152 that require certain volume sizes can be easily accommodated. To doso, a volume 110 through 112 is configured with an arbitrary storagesize 124 that is greater than any required amount expected by hostapplications or operating systems. Since the storage size 124 isindependently selected from any associations to portions of storagedevices 114 through 116 within the volumes 110 through 112, the datastorage system 100-1 does not need to initially provide or allocate theactual amount of storage space in storage device 114 through 116 asspecified in the storage size.

As indicated above, and in particular, with respect to steps 353 and 363in FIGS. 4 and 5, the volumes 110 through 112 provided by this inventionare able to allow multiple hosts 150 through 152 to simultaneouslyaccess data within the same volume 110 through 112. This can beaccomplished in the invention even if the operating systems of thedifferent hosts (e.g. host 150 through 152) are incompatible with eachother with respect to any host-specific access information required foraccessing individual storage devices (e.g. 114 through 116) within thevolumes 110 through 112.

FIG. 6 illustrates an example of multiple hosts 150 through 152accessing the same volume 110 within the data storage system 100-1through a switch 250. Each host 150 through 152 includes a respectivehost bus adapter (HBA) 153-1, 153-2 and 153-3. The host bus adapters 153each contain a respective World Wide Name WWN1, WWN2 and WWN3. The WorldWide Name (WWN) is a unique number or data sequence assigned to eachhost 150 through 152 that serves as a unique identifier for the host.For example, WWN1 for host 150 may include a value such as the MACaddress (i.e. Ethernet networking address) of the host bus adapter153-1. In this particular example, each host 150 through 152 interfacesto an interconnection switch or hub 250, which allows data transfers totake place between the hosts 150 through 152 and the data storage system100-1

When one of the hosts (e.g. host 150) initially attempts to access thedata storage system 100-1 through the switch 250, the host 150 providesan access request (e.g., a poll for volume information) along with thehost's unique World Wide Name (WWN) to the switch 250, as indicated at221 in FIG. 6. The switch 250 then generates and returns a unique ID tothe requesting host 150 (as shown at 224), and forwards (as shown at222) the host's access request, the host's World Wide Name and theassigned ID to the data storage system 100-1. After the initial exchangeof the World Wide Name and the unique identification ID between thehosts 150 through 152 and the switch 250, the hosts 150 through 152thereafter use the unique identification (ID) for any remaining dataaccesses to the volume 110. Generally, as will be explained in greaterdetail, the data storage system 100-1 uses the unique ID (ID1, ID2, ID3and so forth) for a respective host 150 to 152 to identify therequesting host and to determine its World Wide Name. The World WideName is then used to obtain the proper access information (e.g. Block 0)required by a requesting host 150 through 152 to correctly access therequested volume (e.g. volume 110 in this example). The accessinformation (not specifically shown in FIG. 6) is then returned throughthe switch 250 back to the requesting host 150, as indicated at 223 and224.

FIG. 7 provides a more detailed embodiment of the volume 110 within thedata storage system 100-1 which maintains access information 201 for thehosts 150 through 152 for each storage device 114 through 116 that isassociated with the volume 110. As indicated this figure (and asindicated by storage device interfaces 120-1 through 120-3 in FIG. 2),the volume 110, as currently configured, is associated with threestorage devices 114-1, 115-1 and 115-2 within the data storage system100-1.

In this example, all three host computing devices 150 through 152 areable to access the storage devices 114-1, 115-1 and 115-2 within thevolume 110. To do so, each host 150 through 152 during its initialcommunications with the switch 250 (as explained with respect to FIG. 6)provides its respective World Wide Name WWN1, WWN2 and WWN3(collectively called WWN) to the switch 250. In response, the switchprovides each host 150 through 152 with the unique identification, shownas ID1, ID2 and ID3, respectively. The switch 250 then forwards theWorld Wide Name and unique identification ID pairs WWN1/ID1, WWN2/ID2and WWN3/ID3 for each host 150 through 152 to the label manager 130within the data storage system 100-1. Within the volume 110 in FIG. 7,the label manager 130 maintains a login history table 200 and a numberof access information tables 201 (three in this example; 201-1, 201-2and 201-3). As will be explained, in this embodiment, for each volume110 through 112, these tables maintain a database of access informationfor each storage device 114 through 116 that is associated with thevolume.

The login history table 200 stores the World Wide Names 200-1 and theunique identifications 200-2 of each host 150 through 152 that iscurrently able to access data within the volume 110. Each entry (WWN/IDpair) in the login history table 200 is obtained and created once when ahost 150 through 152 initially attempts to access the volume 110 (asillustrated in FIG. 6) via the switch 250. All access attempts from thehosts 150 through 152 after the first use the identification ID1, ID2,and so forth as assigned by the switch 250. As such, the login historytable 200 is used to determine the World Wide Name associated with anaccess attempt based upon the identification ID of the host 150 through152 that is attempting access to the volume 110.

The access information table 201 stores all of the host-specific accessinformation (Column 2, labeled 205, with specific access informationlabeled ID1-0, ID2-0, IDN-0, where N is the index for the ID and theWorld Wide Name) for each host 150 through 152, for each storage devicethat is associated with the volume 110. In this example, since thevolume 110 has three associated storage devices 114-1, 115-1 and 115-2,there are three access information tables 201-1, 201-2 and 202-3, onefor each associated storage device 114-1, 115-1 and 115-2, respectively.Specifically, the access information table 201-1 maintains all of thehost-specific access information (i.e., access information required byeach host 150 through 152, no matter what operating system is used onthat host) for the storage device 114-1, while the access informationtable 201-2 maintains all of the host-specific access information forthe storage device 115-1, and the access information table 201-3maintains the host-specific access information for the storage device115-2.

Each access information table 201 includes a World Wide Name column 204and an access information column 205. The World Wide Name column 204provides an index that can be used to determine the host specific accessinformation 205 (one of ID1-0, ID2-0, ID3-0 and so forth) for arespective host 150 through 152. Thus in this embodiment, lookup in theaccess information tables 201 are based on the World Wide Name (one ofWWN1, WWN2, WWN3 and so forth) for the host 150 through 152, asdetermined by an identification (ID) lookup form the login history table200.

In this particular embodiment, each entry (i.e. each row) in the accessinformation column 205 of table 201-1 stores respective Block 0information for the storage device 114-1 for one of the hosts 150through 152. Also as illustrated, each storage device 114-1, 114-2 and114-3 is comprised of a series of sequential blocks (Block 1, Block 2,Block 3, . . . . Block-X), with Block 0 being removed. The missing Block0 information in each storage device 114-1, 115-1 and 115-2 within thevolume 110 is maintained in column 205 in the respective host-specificaccess information tables 201-1, 201-2 and 203-3. By way of example, theentry WWN2/ID2-0 in table 201-1 contains Block 0 information (identifiedin this illustration as ID2-0) for storage device 114-1 for the host 151which has the World Wide Name WWN2. Note that only access informationtable 201-1 is shown in detail. It is to be understood that accessinformation tables 201-2 and 201-3 have similar access information thatcorresponds to storage devices 115-1 and 115-2, respectively.

Using the mechanisms shown in FIG. 7, the label manager 130 for thevolume 110 is able to simultaneously accept and handle access requestsfor data stored within the storage devices 114-1, 115-1 and 115-2 fromany of hosts 150 through 152. Since Block 0 information is maintainedseparately for each host 150 through 152, each host is able to properlyhandle data transactions in its own particular manner.

It is to be understood that while the label manager 130 is illustratedas being within the volumes 110 through 112 in FIGS. 2 and 7,alternative configurations of a data storage system 100-1 according tothis invention may provide a single label manager 130 that executes onthe processor 106 within the data storage system 100-1.

FIG. 8 provides a flow chart of the processing steps performed byembodiments of the invention which allow multiple hosts (e.g. 150through 152) to access a single volume (e.g., 110), as explained abovewith respect to the example embodiment illustrated in FIG. 7.

In step 401 in FIG. 8, the processing detects an attempted access from ahost computing device 150 through 152 to a volume of data (e.g., 110 inFIG. 7) within the data storage system 100-1. In step 402, theprocessing then determines the identity of the computing device (e.g.,ID1, ID2, and so on) that is attempting to access (as detected in step401) the volume and determines the specific requested storage device(e.g. 114-1, 115-1 or 115-2) within the volume (e.g., 110) for whichaccess is requested. The requested storage device (e.g., 114-1) can bedetermined, for example, based upon the block address of data to be reador written to the volume, as specified in the access request detected instep 401.

In step 403, the processing retrieves the host-specific accessinformation 205 for the requested storage device 114-1, 115-1 or 115-2within the access information table 201. Step 403 uses both the loginhistory table 201 and one or more of the access information tables 201,depending upon the location of data that is being read or written (i.e.,accessed). The login history table 200 is used to determine the WorldWide Name (WWN) for the host 150 through 152 that is requesting accessto one or more of the storage devices 114-1, 115-1 and/or 115-2, basedupon the host identification ID determined in step 402. Once step 403has obtained the World Wide Name WWN for the requesting host, the properBlock 0 access information 205 (i.e., one of ID1-0, ID2-0, ID2-0) can beretrieved from the appropriate access information table 201-1, 201-2and/or 201-3. In this manner, each host 150 through 152 can haveseparate access information retained within the volumes 110 through 112,which allows variations in operating systems or host architectures tohave little effect on data storage and volume access requirements.

Once the access information 205 has been determined for the requestinghost having the World Wide Name as determined by step 403, step 404determines if the volume information (e.g., storage size 124, identifier122) maintained within the volume (e.g., the volume 110 in FIG. 2) isequal to any volume information that may be contained or that may existwithin the access information 205 obtained from the respective accessinformation table 201 that is specific to the requesting host 150through 152. In certain instances, the Block 0 access information 205,which is originally created by each of the hosts 150 through 152, maycontain information such as an amount of storage originally associatedwith the volume 110 or the individual storage device 114-1. If this isthe case, step 405 of the invention replaces the information originallycreated by the host in its host-specific block 0 access information 205with the information as configured within the volume (i.e., one of 110through 112).

As an example, suppose host 150 initially writes a five gigabyte sizeparameter indicating a total amount of storage space (five gigabyte)that is initially associated with volume 110 (from the perspective ofhost 150) in its Block 0 information (ID1-0 in column 205) in table201-1 for storage device 114-1. Recall that the five gigabyte valuepresented to the host may be from the storage size location 124 withinthe volume. Recall that the storage size value 124 of the volumes 110through 112 may change over time according to the embodiments of theinvention. As such, in step 404, if the size parameter written by host150 in its Block 0 information (obtained in step 403) does not properlycoincide with the storage size 124-1 (FIG. 2) for the volume 110, step405 replaces the size parameter value (i.e., the Block 0 value) with thevolume storage size value maintained in storage size 124-1. This ensuresthat techniques employed by hosts 150 through 152 to determine storagesizes or other information cannot circumvent the features of volumes 110through 112 of the invention.

When step 405 is complete, or if step 404 determines that the accessinformation 205 does not contradict the volume information (e.g.,storage size values 124, identifier values 122, and so forth), then step406 provides the access information to the requesting host computingdevice 150 through 152 (e.g. 150 in this example). The accessinformation includes any replaced volume information, if step 405 wasexecuted. In this manner, the processing steps 401 through 406 allowmultiple hosts 150 through 152 to access a single volume 110 through 112at one time.

In embodiments of the volume entries 110 through 112 of this invention,the associated identifier 122 (FIG. 2) can be a persistentidentification. By persistent identification, what is meant is that theidentifier 122 used to reference the volume 110 through 112 is the samefor one or more host computing devices 150 through 152. Thus, host 150,for example, perceives the availability of volume 110 using the samevalue of identifier 122 as, for example, hosts 151 and/or 152.Persistent identifiers 122 are also “visible” and accessible to otherdata storage systems. This feature of the invention allows a volume 110through 112 to have other associated data storage devices (other than114 through 116) located on other data storage systems (other than100-1) that are different than data storage system 100-1.

FIG. 9 illustrates this aspect of the invention. In FIG. 9, two datastorage systems 100-1 and 100-2 are illustrated. Each is aware, via theuse of the persistent identifiers 122, of all of the volumes availablewithin the other data storage system. Thus data storage system 100-2 can“see” volumes 110 through 112 in data storage system 100-1, and datastorage system 100-1 can “see” volume 112-2 within data storage system100-2. The two data storage systems 100-1 and 100-2 can interconnect 107via remote interfaces 105 in each data storage system 100-1 and 100-2 toallow volumes to access data in other volumes.

In the specific illustrated example, volume 112-1 in data storage system100-1 uses its remote interface 126-3 to reference 107, via the remoteinterface 105, data stored within the volume 112-2 which is maintainedwithin the data storage system 100-2. This aspect of the inventionallows volumes to obtain access to data stored remotely, and to presentthe remotely stored data (i.e., data stored in volume 112-2) to hosts(e.g., 150 through 152 coupled to data storage system 100-1) as if thedata were stored locally. Since the volumes of the invention, asexplained above, can have storage associated and disassociated atvarious times, without effecting host activity, volumes can remain onone data storage system 100-1 while referencing all of their data fromanother data storage system 100-2.

In embodiments of this invention, it is also to be understood that theexact location of the volume data structures 110 through 112 is notlimited to existing within the channel director 102. For example,another component within the data storage system 100-1 such as the cachememory 103 can maintain the volume entries 110 through 112. However,since in the example data storage system 100-1, the channel director 102provides the physical interfaces (i.e. 156 through 158 in FIG. 1)between each host 150 through 152 and the data storage system 100-1, thevolume entries 110 through 112 are maintained therein. It is also to beunderstood that the processing steps of the flow charts explained aboveare generally preferably carried out by the processor 106 within thedata storage system 100-1. Alternatively, there may be a dedicatedchannel director processor with the channel director 102 that handlesthe processing associated with the volumes of this invention.

While this invention has been particularly shown and described withreferences to preferred embodiments thereof, it will be understood bythose skilled in the art that various changes in form and details may bemade therein without departing from the spirit and scope of theinvention as defined by the appended claims. The foregoing descriptionof embodiments of the invention are not intended to be limiting. Rather,any limitations to the invention are presented in the following claims.

1. A method comprising: maintaining a size parameter associated with avolume in a storage system, the size parameter representing acorresponding size of the volume for storing data; maintainingreferences to specify storage space in the storage system allocated foruse by the volume; and via the size parameter, providing an appearanceto at least one computer having access to the volume that thecorresponding size of the volume is different than an amount of actualstorage space of the volume for storing the data.
 2. A method as inclaim 1 further comprising: maintaining at least one reference of thereferences as a null value that does not reference any actual storagespace associated with the storage system.
 3. A method as in claim 2further comprising: changing the at least one reference from the nullvalue to a non-null reference value in order to add an amount of storagespace to the volume.
 4. A method as in claim 1 further comprising:maintaining each of the references as a null value that does notreference any corresponding storage space associated with the storagesystem.
 5. A method as in claim 1, wherein providing the appearance tothe at least one computer includes providing the appearance to the atleast one computer that the corresponding size of the volume is largerthan the amount of actual storage space of the volume as defined by thereferences.
 6. A method as in claim 1 further comprising: allowing theat least one computer continuous access to the volume while allocatingmore storage space in the storage system to the volume.
 7. A method asin claim 6, wherein allocating more storage space to the volume occursin response to detecting that an available amount of unused storagespace allocated for use by the volume crosses a threshold.
 8. A methodas in claim 1 further comprising: in response to a usage analysis,modifying at least one of the references to change the amount of actualstorage space allocated for use by the volume.
 9. A method as in claim 1further comprising: maintaining the size parameter associated with thevolume to be a substantially fixed value more than the amount of actualstorage space associated with the volume.
 10. A method as in claim 1,wherein maintaining the references to specify the storage space in thestorage system allocated for use by the volume includes maintaining thereferences to point to storage devices of the storage system for storingthe data.
 11. An interface supporting access to a storage system, theinterface comprising: a processor; a memory unit that storesinstructions associated with an application executed by the processor,the processor supporting operations of: maintaining a size parameterassociated with a volume in the storage system, the size parameterrepresenting a corresponding size of the volume for storing data;maintaining references to specify storage space in the storage systemallocated for use by the volume; and via the size parameter, providingan appearance to at least one computer having access to the volume thatthe corresponding size of the volume is different than an amount ofactual storage space of the volume for storing the data.
 12. Aninterface as in claim 11 further supporting operations of: maintainingat least one reference of the references as a null value that does notreference any actual storage space associated with the storage system.13. An interface as in claim 12 further supporting operations of:changing the at least one reference from the null value to a non-nullreference value in order to add an amount of storage space to thevolume.
 14. An interface as in claim 11 further supporting operationsof: maintaining each of the references as a null value that does notreference any corresponding storage space associated with the storagesystem.
 15. An interface as in claim 11, wherein providing theappearance to the at least one computer includes providing theappearance to the at least one computer that the corresponding size ofthe volume is larger than the amount of actual storage space of thevolume as specified by the references.
 16. An interface as in claim 11further supporting operations of: allowing the at least one computercontinuous access to the volume while allocating more storage space inthe storage system to the volume.
 17. An interface as in claim 16,wherein allocating more storage space to the volume occurs in responseto detecting that an available amount of unused storage space allocatedfor use by the volume crosses a threshold.
 18. An interface as in claim11 further supporting operations of: in response to a usage analysis,modifying at least one of the references to change the amount of actualstorage space allocated for use by the volume.
 19. An interface as inclaim 11, wherein maintaining the references to specify the storagespace in the storage system allocated for use by the volume includesmaintaining the references to point to storage devices of the storagesystem for storing the data.
 20. A computer program product including acomputer-readable medium having instructions stored thereon forprocessing data information, such that the instructions, when carriedout by a processing device, enable the processing device to perform thesteps of: maintaining a size parameter associated with a volume in astorage system, the size parameter representing a corresponding size ofthe volume for storing data; maintaining references to specify storagespace in the storage system allocated for use by the volume; and via thesize parameter, providing an appearance to at least one computer havingaccess to the volume that the corresponding size of the volume isdifferent than an amount of actual storage space of the volume forstoring the data.